Repository navigation
fix: separate privileged tools from node updates - #3
Merged
Merged
Conversation
Co-authored-by: aperod-network <aperod-network@users.noreply.github.com>
aperod-network
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Node/API/validator updates no longer load the old tool synchronizer or replace root-executed backup/deployment tools. Remote validator updates likewise retain installed tools. The manual helper requires an independently approved tool SHA256 and verifies staged bytes/syntax before replacement; a clean local commit or node pin is not tool approval.
Complete immutable 625-file tree passed history/path policy, redacted secret scans, Go build/vet/govulncheck and the full Go suite before the first upload. New temporary-Git regressions cover dirty/clean unauthorized sources, symlinks, self-manifests, staged mutation and actual former sync section; installed bytes/modes remain unchanged and payload markers never execute.
No production runtime state changed. This addresses tool replacement, not a claim of a complete root bootstrap-package trust lifecycle.